Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1124

reference: 675-tree-1
name: 1124
tree-preservation-order: undefined
675-tpo-1
uprn
address-text
point: POINT (-1.018035 50.879867)
geometry: MULTIPOLYGON (((-1.017979 50.879861,-1.017981 50.879872,-1.017989 50.879882,-1.018002 50.879891,-1.018017 50.879896,-1.018035 50.879898,-1.018052 50.879896,-1.018068 50.879891,-1.018081 50.879883,-1.018089 50.879873,-1.018092 50.879862,-1.018090 50.879851,-1.018082 50.879841,-1.018070 50.879833,-1.018054 50.879828,-1.018036 50.879826,-1.018019 50.879827,-1.018003 50.879832,-1.017990 50.879840,-1.017982 50.879850,-1.017979 50.879861)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL